Various fixes#10702
Open
Frauschi wants to merge 7 commits into
Open
Conversation
Ensure a signer signature is actually verified before reporting a PKCS7 SignedData object as verified, and add a regression test.
Require the keyCertSign key usage on non-root intermediate CAs added during path building when a KeyUsage extension is present, per RFC 5280. Adds a regression test.
Ensure a peer's certificate form (X.509 vs raw public key) matches the negotiated certificate type, defaulting to X.509 when none was negotiated, on both the client and server. Adds RPK regression tests covering both directions.
|
Contributor
Author
Only exempt the missing-certificate check during the initial handshake; once a post-handshake CertificateRequest is outstanding the server again requires the client certificate (and its CertificateVerify). Adds a post-handshake auth test.
…size Regenerate the SP backends so the ECDH secret generators check the caller's buffer against the number of bytes actually written. Adds a P-384/P-521 buffer-size regression test.
Reject a negative read length in the memory BIO read path so it cannot bypass the signed bounds checks and reach a wild copy. Adds a regression test.
JacobBarthelmeh
previously approved these changes
Jun 16, 2026
Contributor
|
wolfSSL-Fenrir-bot
left a comment
There was a problem hiding this comment.
Fenrir Automated Review — PR #10702
Scan targets checked: wolfcrypt-bugs, wolfcrypt-rs-bugs, wolfcrypt-src, wolfssl-bugs, wolfssl-src
No new issues found in the changed files. ✅
Contributor
|
Retest this please Jenkins CAVP test make check failure "wolfSSL error: port number cannot be 0" |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hardening and correctness fixes for certificate, TLS, and crypto paths
A set of defensive fixes across several subsystems, each in its own commit with an accompanying regression test:
All changes are covered by new unit tests; full test suite passes. Fixes findings 1, 2, 3, 6, 12, and 29 of zd21992. Needs https://github.com/wolfSSL/scripts/pull/588.